home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000426_news@newsmaster….columbia.edu _Tue Apr 14 22:20:30 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id WAA29904
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 14 Apr 1998 22:20:30 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id WAA01052
for kermit.misc@watsun; Tue, 14 Apr 1998 22:20:29 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: timeout on k95
Date: 15 Apr 1998 02:20:26 GMT
Organization: Columbia University
Lines: 27
Message-ID: <6h15ha$2c2$1@apakabar.cc.columbia.edu>
References: <6ggtct$7me$1@news.ncal.verio.com> <6giigg$9ot$1@apakabar.cc.columbia.edu> <6h0ul6$m1s$1@news.ncal.verio.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:8630
In article <6h0ul6$m1s$1@news.ncal.verio.com>, den <dirvine@psln.com> wrote:
: I am sorry Frank, but it is not the system logging me out. I can use a
: different terminal emulation program and it can set there all day without
: being logged out. Only K95 cuts off.
:
Dennis:
I examined the debug.log that you sent me and as I pointed out to you
the TCP/IP stack is reporting ECONNRESET errors. This is a fatal
socket error which means that your TCP/IP stack has received a packet
or other data that it was not expecting. This usually means that
more than one machine on your network is using the same IP address.
A ECONNRESET error is fatal and Kermit 95 treats it that way. Kermit 95
is behaving correctly. If another package decides to ignore this error
then it is leaving you open to having your terminal session hijacked
or otherwise tampered with.
The proper place to look is at your network. Do not blame Kermit 95
for this problem.
- Jeff
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org